Same problem on macOS 27 beta

A Universal app that supports widgets is a very common scenario, so I’m surprised there is so little discussion or documentation about this issue. I’ve tried every workaround I could think of, but nothing has helped. I was hoping to compare notes with other developers, but you are the only person I’ve found reporting the same problem.

Hi Ian, Have you found any workaround or fix for this issue? We are seeing essentially the same behavior in a Universal app with shared iOS/macOS WidgetKit code: The widget is fully configurable on iOS. It works correctly on macOS 15. It also worked on macOS 26 a few months ago. On macOS 26.5.2, choosing “Edit Widget” makes the widget turn gray and float above other windows, but the configuration UI never appears. The same widget configures correctly in WidgetKit Simulator. The widget’s URL action still routes correctly to the native Mac app. We have tested many possible causes, including changing the macOS-only bundle identifier, widget kind, App Intent type/class name, cleaning build data, removing older app copies, reinstalling the TestFlight build, and restarting the Mac. None of these changed the behavior. Disabling or enabling iPhone Widget Mirroring also made no difference. Our current suspicion is a macOS 26 system-level regression in the WidgetKit/App Intents configuration path, possibly related to the deeper integration of iPhone Widgets and iPhone Mirroring. The fact that the same code works on iOS, macOS 15, and in the Simulator makes an app-logic or packaging problem seem unlikely. Have you been able to reproduce this on a newer macOS build, or find any workaround?

I found the way: using the same Icon Name for app created with Icon Composer and the old asset for visionOS app icon.

Close this post as no reply

Close this post after a long time.

No solution

Feedback ID: FB18792279

It seems that the “.tint” modifier does not work for “Menu” either, even if .menuType(.button) is specified.

@DTS Engineer Thank you for the detailed instructions. I followed each step carefully and achieved the "same" results as outlined in your guide (with different identifiers, of course). Specifically, I generated a new provision profile UUID and group identifiers starting with “group.” And in the provision profile file with the new UUID, there is key "com.apple.security.application-groups" with same value as set in Xcode. However, after uploading the archive to the App Store via Xcode Organizer, I am still encountering the same error as before. ... This value should be a string or an array of strings, where each string is the “group” value or your Team ID, followed by a dot (“.”), followed by the group name. If you're using the “group” prefix, verify that the provisioning profile used to sign the app contains the com.apple.security.application-groups entitlement and its associated value(s). ... Additionally, when testing the widget using WidgetKit Simulator on macOS, I receive error message continually when show the timeline. The operation couldn't be completed. (CHSErrorDomain error 1103.) Could you kindly advise on a solution for this as well?

The ModelConfiguration is what you are looking for. I do not get chance to try it, but the WWDC video shows the way like: let people = ModelConfiguration(..., cloudKitContainerIdentifier: "com.xxx.xxx") let container = try ModelContainer(for: ..., people) I understand that SwiftData is a set of swift classes. However, I have some concerns about using them directly in the UI, as shown in the videos and the examples. This may lead to some problems: Performance issue. For instance, if a record contains some images, how can I handle them efficiently with SwiftData? I don't want to load all the image data in memory, but rather cache them in files and load the URL in the view model. Complicated logic. Using SwiftData models in the UI may be convenient for coding, but sometimes the logic may become too complex. We may need to create other view models based on the basic models. But SwiftData is not a lightweight variable, and I don't know how to track the changes of the SwiftData models in other custom @Observeable models. I have no more CoreData experience, would you please help to suggest the way to use SwiftData for my preceding concerns?

One of the benefits of SwiftData is that it allows us to access CloudKit containers directly without having to deal with CKRecord and other low-level details. However, I am wondering which solution is better for an app that has a complex view model. Is SwiftData suitable for handling complex data structures and relationships? Or should we use the the traditional way to code the view models with CKSyncEngine for sync?

Same problem here.